-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config update for project-factory #1207
Conversation
… one column with header OTHER_TARGETS
WalkthroughWalkthroughThe recent changes improve the handling of boolean configuration settings in the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- utilities/project-factory/src/server/config/index.ts (1 hunks)
Additional comments not posted (3)
utilities/project-factory/src/server/config/index.ts (3)
21-21
: LGTM! Explicit boolean evaluation improves clarity.The change ensures that the environment variable
IS_CALL_GENERATE_WHEN_DELIVERY_CONDITIONS_DIFFER
is strictly evaluated as a boolean value, preventing unintended truthy evaluations.
23-23
: LGTM! Explicit boolean evaluation improves clarity.The change ensures that the environment variable
EXCLUDE_HIERARCHY_TYPE_FROM_BOUNDARY_CODES
is strictly evaluated as a boolean value, preventing unintended truthy evaluations.
24-24
: LGTM! Explicit boolean evaluation improves clarity.The change ensures that the environment variable
EXCLUDE_BOUNDARY_NAME_AT_LAST_FROM_BOUNDARY_CODES
is strictly evaluated as a boolean value, preventing unintended truthy evaluations.
* updated readmeconfig for sheet * added cache for generating target template when only delivery conditions change * added logic for having only 18 target columns if exceed i will create one column with header OTHER_TARGETS * updated config to fetch from devops accordingly * updated config for project -factory
No description provided.